An issue with ufo2fdk is being fixed. see http://code.typesupply.com/changeset/1154 This will be embedded in the next version of RoboFont thanks

this is a v1.1 bug and will be solved in the next version there are no print statements anymore captured from FDK after it fails some where (like in your example)

I think you disabled "Use Embedded FDK" and on your local machine there is no FDK installed, so RoboFont cannot find anything to generate the binary file. see http://doc.robofont.com/documentation/workspace/preferences/misc/

No, I don't have any features written. Until yesterday test installing worked completly fine. Now, I just amended the design of a letter and test installing doesn't work anymore. I have as well tried to test install previous versions of the font (that I have been installed sucessfully), but it wouldn't test install them anymore. Thanks a lot for your help!

Thanks Frederik for such a prompt and thorough response (as always!).

Indeed, there was a stray single point on top of another point. That script worked great, thank you.

changed: http://doc.robofont.com/documentation/export/

Thanks, will look at it!

ufo2fdk is embedded and by default using the embedded FDK, you can disable the use of of the internal FDK in the preferences. The file menu option "Generate" or through scripting font.generate(...) is using FDK to build the binaries. It's up to you if you want to use the embedded FDK or a custom installed version on your local HD.

Thank you! btw, I'm not getting forum reply posts per email :(

True but… "Most" but not "all" actions, maybe? :) At some point there may be an UI issue if all extra actions have to be found in the scripts folder. (and as well documented the API is, the UI customization still requires extra scripting skills)